New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Add ANGULAR_PACKAGE to snapshot builds #31900
Conversation
Ivy snapshots no longer contain metadata.json which breaks the detection logic for Angular Package Format (APF) in npm/yarn install. This PR adds ANGULAR_PACAKGE as a magic file to denote APF. See bazelbuild/rules_nodejs#927
But we still need a solution for 3rd-party packages, once we start recommending publishing packages built for ivy, right? Is this tracked somewhere (e.g. a Jira ticket)? |
@@ -70,6 +70,7 @@ function publishRepo { | |||
fi | |||
echo `date` > $REPO_DIR/BUILD_INFO | |||
echo $SHA >> $REPO_DIR/BUILD_INFO | |||
echo 'This file is used by the npm/yarn_install rule to detect APF' > $REPO_DIR/ANGULAR_PACKAGE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a link to some more info (e.g. an issue on rules_nodejs
with an explanation) or a comment explaining that this is due to the absence of metadata.json
files under ivy would be helpful for posterity 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm this only affects snapshots pushed to GH. should this file also appear in any npm packages we build? Will Angular publish ivy-only release artifacts anytime?
FYI I added the merge label, I think this was just stuck? |
Ivy snapshots no longer contain metadata.json which breaks the detection logic for Angular Package Format (APF) in npm/yarn install. This PR adds ANGULAR_PACAKGE as a magic file to denote APF. See bazelbuild/rules_nodejs#927 PR Close angular#31900
Ivy snapshots no longer contain metadata.json which breaks the detection logic for Angular Package Format (APF) in npm/yarn install. This PR adds ANGULAR_PACAKGE as a magic file to denote APF. See bazelbuild/rules_nodejs#927 PR Close angular#31900
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Ivy snapshots no longer contain metadata.json which breaks the detection logic for
Angular Package Format (APF) in npm/yarn install.
This PR adds ANGULAR_PACAKGE as a magic file to denote APF.
See bazelbuild/rules_nodejs#927
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information